I have the same problem after installing Windows 8: "Your PC run into a problem and need to restart"

Repeating restart after my PC shutting down, restart, or downloading anything.

• Changed type Arthur XieMicrosoft contingent staff, Moderator Monday, December 03, 2012 8:16 AM

Hi!

I am experiencing the same problem, many times now.

Here is the link:

https://skydrive.live.com/#cid=6E82E63E9B0508F7&id=6E82E63E9B0508F7%21127.

Please help, thanks!

• Edited by felmarrowell Thursday, January 31, 2013 3:06 PM

Finally. Here are my dmp files. Can you check what is wrong? I've had a lot of Bsod's recently.

https://skydrive.live.com/redir?resid=9CFE2D2560327DE7!163

• Edited by I Really need help 27 Saturday, February 09, 2013 11:48 PM

Oh Ok thanks

THe bsod file collection app works with windows 8 too right?

Also i need to run both right?

• Edited by I Really need help 27 Sunday, February 10, 2013 12:28 AM

I haven't overclocked anything. My CPU, GPU, and RAM haven't been overclocked. I will update my Atheros drivers. What is AV?

• Edited by I Really need help 27 Monday, February 11, 2013 10:00 PM

please help me.. my computer has too many problems.. it restarts itself too many times and doesn't open normally... please here are my files... 
https://skydrive.live.com/redir?resid=7F37A8F2D63A8078!204

p.s. i have wrote before, but the problem still continues. :(

• Edited by pc.alvin Thursday, February 14, 2013 6:39 AM

https://docs.google.com/file/d/0Bx0fRBSYFJkGWEp3ODhPck5IMk0/edit?usp=sharing

[opening .dmp file in windbg shows

BugCheck D1, {b0, 2, 0, fffff88001770d3d}]

http://blogs.msdn.com/b/ndis/archive/2006/11/04/what-causes-a-bug-check-0xd1-irql-not-less-or-equal.aspx

 (Microsoft search for
    bugcheck d1
)

<quote>

This bugcheck can only be fixed by the engineer that developed the driver.  You should check with the manufacturer to see if there is an updated driver to download.

</quote>

So, your only problem now is knowing what is "the driver".   ; }

Try some of the hints that have been left by some of the previous posts?...

Otherwise, first clue would be that 4th parameter which looks like an address

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx

(BING search for
    bugcheck d1  site:msdn.microsoft.com
)

<quote>

4	Address that referenced memory

</quote>

Good guess!

The analyze command suggests NETIO.

lm command shows that is

fffff880`01737000 fffff880`017a6000   NETIO    T (no symbols)

Compare:             fffff88001770d3d      (it fits between both addresses, beginning and end)

So, that looks consistent with that detail.  

Who owns  NETIO and what else is known about it from the dump?

I think either Andre or Exotic Hadron have hinted that is possible in windbg.

However, on your own system, given this clue, you could do that yourself with more conventional end-user techniques..

PS F:\Windows\System32\Drivers> get-item netio.sys | fl *

So, that shows that the module issuing the bugcheck is probably not the problem module.

Does the analyze report give any more clues?...

Maybe.   Looks like it should from Andre's examples.   But I'm on W7 so I think I may have to wait until I get back to W8.   ; )

 

HTH

 
Robert
---

• Edited by Robert Aldwinckle on forumsMVP Sunday, June 02, 2013 4:18 AM This editor is still broken.

update the driver epfwwfpr.sys:

"Windows Filtering Platform"?   What's that?   FWIW I don't even have it--anywhere.   Maybe he doesn't need it too?   (Then disabling it would probably change the symptom.)

http://msdn.microsoft.com/en-us/windows/hardware/gg463267.aspx

Sounds like this could be another victim of an as yet unknown misuser.

• Edited by Robert Aldwinckle on forumsMVP Sunday, June 02, 2013 5:17 PM Microsoft search for "windows filtering Platform"

same thing happened with windows 7 but MS released a hotfix for it but so far can not find one for windows 8.

In that case check your WinSxS to see if there is an LDR version of it.   Perhaps your Hotfix will be there?

Coincidentally I have been experimenting with PowerShell recently in this area:

PS C:\Windows\WinSxS> dir *xpspr* | foreach-object {dir $_\xpsprint.dll} | sort-object LastWriteTime | select -Property LastWriteTime, @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}}  | fl *

So, that was with xpsprint.dll.   Modify it how ever you need to to find your epfwwfpr  modules.   Note that the first stage of the pipeline is just an optimizer so we don't have to do a recursion all the way down to the file level for the whole WinSxS archive.

 
Good luck

 
Robert
---

• Edited by Robert Aldwinckle on forumsMVP Sunday, June 02, 2013 7:28 PM Typo

i don't know that you solved the problem or not , but i found the cause of this problem on my laptop ( Vaio f series ).

i test all drivers one by one and finally i found the problem source .

here is the cause :

1- Original - Renesas Electronics USB 3.0 Host Controller

and

2- Renesas Electronics USB 3.0 Host Controller Update

these are USB3.0 drivers that i downloaded them previously from SONY.COM .

in my case i uninstall them and now the problem completely removed and computer works properly .

hope this can help you and others with similar problem . 

this is my mini dump files. please help me.

https://skydrive.live.com/redir?resid=7708C4ED478E427B!147

I have following link for you to my minidump files... Please guide me...

https://skydrive.live.com/redir?resid=F0A9072E12537F6E!344&authkey=!ABs_khij6T-UTPY

Thanx

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001d, The subtype of the bugcheck:
Arg2: fffffa80097ef390
Arg3: fffff8a00d518e00
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x10e_1d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88000a3d55d to fffff80329462440

STACK_TEXT:  
nt!KeBugCheckEx
watchdog!WdLogEvent5_WdCriticalError
dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBufferIteration
dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource
dxgmms1!VIDMM_GLOBAL::PurgeAllocation
dxgmms1!VIDMM_SEGMENT::PurgeContent
dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand
dxgmms1!VidMmiProcessSystemCommand
dxgmms1!VidSchiSubmitSystemCommand
dxgmms1!VidSchiSubmitQueueCommand
dxgmms1!VidSchiSubmitQueueCommandDirect
dxgmms1!VidSchiSubmitCommandPacketToQueue
dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait
dxgmms1!VIDMM_GLOBAL::PurgeAllSegments
dxgmms1!VidMmPurgeAllSegments
dxgkrnl!VIDMM_EXPORT::VidMmPurgeAllSegments
dxgkrnl!ADAPTER_RENDER::PurgeSegments
dxgkrnl!ADAPTER_RENDER::Stop
dxgkrnl!DXGADAPTER::Stop
dxgkrnl!DpiPowerArbiterThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread


    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Mar 29 03:27:04 2013 

update the AMD driver:

http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-10WINBetaDriver.aspx